System and Method for Modular Construction of Executable Programs Having Self-Contained Program Elements

ABSTRACT

A method for performing a fault tolerant automated sequence of computer implemented tasks including, presenting for selection by a user a plurality of pre-programmed elements, each pre-programmed element being independently executable relative each other pre-programmed element, receiving from the user a selection of one or more of the pre-programmed elements and a sequence for performing each pre-programmed element to form an exemplary routine, creating an instance of the exemplary routine, the instance of the exemplary routine including an instance of each of the selected pre-programmed elements arranged for performance in accordance with the sequence and configured to perform tasks defined by the pre-programmed elements and the sequence, initiating implementation of the instance of the exemplary routine by initiating performance of the instances of the pre-programmed elements in accordance with the sequence, and executing each instance of the pre-programmed elements according to the sequence.

CROSS-REFERENCE TO RELATED APPLICATIONS

This application claims the benefit of U.S. Provisional Pat. ApplicationNo. 63/156,205 filed Mar. 3, 2021 entitled “System and Method forModular Construction of Executable Programs Having Self-ContainedProgram elements”, which is incorporated by reference herein in itsentirety.

BACKGROUND OF THE INVENTION

The present invention generally relates to a modular tool for processsynchronization programs and, more particularly, to a module tool forconstruction of computer implemented process synchronization programs,such as programs used to automate customer service tasks.

BRIEF SUMMARY OF THE INVENTION

In one embodiment there is a method for performing a fault tolerantautomated sequence of computer implemented tasks comprising presentingfor selection by a user a plurality of pre-programmed elements, eachpre-programmed element being independently executable relative eachother pre-programmed element such that an output of any of thepre-programmed elements is not a direct input to any other of thepre-programmed elements. The method further includes receiving from theuser a selection of one or more of the pre-programmed elements and asequence for performing each pre-programmed elements in the selection toform an exemplary routine. The method further includes creating aninstance of the exemplary routine in response to a request to implementthe exemplary routine, the instance of the exemplary routine includingan instance of each of the selected pre-programmed elements arranged forperformance in accordance with the sequence and being configured toperform tasks defined by the pre-programmed elements and the sequence.The method further includes initiating implementation of the instance ofthe exemplary routine by initiating performance of the instances of thepre-programmed elements in accordance with the sequence and executingeach instance of the pre-programmed elements according to the sequence.

In some embodiments, each independently executable pre-programmedelement does not require data generated from another pre-programmedelement to complete. In some embodiments, each independently executablepre-programmed element completes using data from data field that is atleast one of: i) populated in the data field before the creating of theinstance of the exemplary routine and ii) updated after the initiatingof the implementation of the instance. In some embodiments, the methodfurther includes transmitting a notification that at least one instanceof a pre-programmed element did not execute to completion wherein thenotification includes at least one of: i) all instance of exemplaryroutines that are in a failed state at a time the notification istransmitted; ii) the instances of a pre-programmed elements associatedwith each instance of exemplary routines that are in the failed state;iii) the instance of the exemplary routine; iii) a number of retriesassociated with each instance of the exemplary routine in the failedstate; iv) a database object associated with each instance of theexemplary routine in the failed state.

In some embodiments, the method further includes updating one or more ofthe pre-programmed elements of the exemplary routine after theinitiating implementation step and creating a subsequent instance of theexemplary routine in response to a subsequent request to implement theexemplary routine after the updating step, the subsequent instance ofthe exemplary routine including an instance of the one or more updatedpre-programmed elements of the exemplary routine. In some embodiments,the method further includes simultaneously implementing a plurality ofinstances of the same exemplary routine. In some embodiments, the methodfurther includes simultaneously implementing at least one instance ofthe exemplary routine and at least one instance of the sub sequentexemplary routine.

In some embodiments, at least some of the instances of the exemplaryroutine are initiated at a different time than other instances of thesame exemplary routine that are being simultaneously implemented. Insome embodiments, updating the one or more of the pre-programmedelements includes receiving and storing revised code for performing atask. In some embodiments, the method further includes detecting anerror that prevents completion of at least one instance of thepre-programmed elements and terminating the implementation of theinstance of the exemplary routine upon detection of the error withoutuser intervention. In some embodiments, the method further includesafter the detecting step and before the terminating step, attempting tore-implement at least one instance of the pre-programmed elementsassociated with the detected error.

In some embodiments, the method further includes detecting a triggerevent that triggers, without user intervention, a re-initiation of theperformance of the instance of at least one of the pre-programmedelements and wherein an error state that prevents the completion of theat least one instance arises after a sub sequent trigger event isdetected following a pre-selected number of re-initiations of theperformance of the at least one instance of the pre-programmed element.In some embodiments, the method further includes defining a retrythreshold value for each of the pre-programmed elements and after thedetecting step and before the terminating step, attempting tore-implement the at least one instance of the pre-programmed elementsassociated with the detected error in accordance with the retrythreshold value.

In some embodiments, the method further includes during implementationof the instance of the exemplary routine, detecting the absence ofprescription authorization data needed to complete the implementation ofthe instance of the exemplary routine. The method may further includebased on the absence of the prescription authorization, automaticallytransmitting an authorization form to an authorizing entity, receivingan authorization facsimile of a completed form in response to theautomatic transmitting and automatically populating a prescriptionauthorization field based upon the received facsimile. In someembodiments, the method further includes receiving a datafile containingoptical character recognition data associated with the authorizationfacsimile. In some embodiments, the method further includesautomatically storing the datafile containing optical characterrecognition data in a secure database based upon the automaticallypopulating the prescription authorization field.

In some embodiments, regular expression matching logic is applied to thedatafile containing optical character recognition data to identify dataassociated with at least one of: owner name, pet name, record identifierfor a prescription, clinic name, authorization status, refillauthorization data, reason for requiring compound prescription andcombinations thereof. In some embodiments, the simultaneouslyimplemented plurality of instances of the exemplary routines are complexoperations as described in at least one of the previous embodiments. Insome embodiments, at least 100 complex routines are performedsimultaneously per minute.

In some embodiments, the method further includes adding or removing atleast one selected pre-programmed element from the exemplary routineafter the initiating implementation step and creating a subsequentinstance of the exemplary routine in response to a subsequent request toimplement the exemplary routine after the adding or removing step, thesubsequent instance of the exemplary routine reflecting the addition orremoval of the at least one selected pre-programmed element inaccordance with the adding or removing step. In some embodiments, one ormore data objects are not populated at the time of creating of aninstance of the exemplary routine but are populated in order for theinstance of the exemplary routine to complete. In some embodiments,logging exists out-of-band.

In some embodiments, the method further includes receiving from a user,trigger instructions defining at least one trigger condition. Thecreating of an instance of the exemplary routine is based upon arecognition that at least one of the trigger conditions has been met. Insome embodiments, at least one of the trigger conditions is a change indata state. In some embodiments, each pre-programmed element operates onone or more of: i) a defined data set and ii) a variable data set. Insome embodiments, the method further includes after detecting an errorthat prevents completion of at least one instance of the pre-programmedelements, receiving an intervention to complete the at least oneinstance of the pre-programmed element. In some embodiments, theexemplary routine further comprises data object mapping that defines foreach exemplary routine the location of data required by one or morepre-programmed elements within the exemplary routine.

In some embodiments, the data object mapping is at least in part definedwithin the pre-programmed elements. In some embodiments, the methodfurther includes simultaneously implementing one or more instances of anexemplary routine by implementing instances of pre-programmed elementsin parallel. In some embodiments, the method further includes sequencingthe performance of pre-programmed elements by delaying instructions toimplement a pre-programmed element until at least one of anotherpre-programmed element achieves a predefined state. In some embodiments,the predefined state includes at least one of: i) a completion state;ii) a failure state. In some embodiments, the completion state includesat least a partial completion and the failure state includes failureafter a predetermined number of retries.

In some embodiments, at least one pre-programmed element is along-running pre-programmed element that is programmed to cause otherpre-programmed elements within an instance of the exemplary routine inwhich an instance of the long-running element is included to at leastone of: i) pause execution until the long-running element reaches acompletion state; ii) delay completion until the long-running elementreaches the completion state. In some embodiments, the completion stateincludes at least one of: i) complete; ii) partial complete; iii) failedto complete; iv) not started and v) delayed. In some embodiments, themethod further includes one of completing the instance of the exemplaryroutine using the state of the respective instances of pre-programmedelements after the instance of the exemplary routine has been createdwherein subsequent to the time the instance of the exemplary routine hasbeen created, a change is made to the exemplary routine upon which theinstance of the exemplary routine is based; and interrupting theinstance of the exemplary routine after receiving a call to interruptthe instance of the exemplary routine based upon call to create a newinstance of the exemplary routine using a data site that is also used bythe instance of the exemplary routine and the dataset includes a flagset to cause the interruption of the instance of the exemplary routine.

In some embodiments, the method further includes interrupting executionof the instance of the exemplary routine upon receipt of a triggeringevent. In some embodiments, the method further includes interruptingexecution of the instance of the exemplary routine upon receipt of apredetermined number of triggering events including at least one of: i)a network timeout; and ii) a system error. In some embodiments, thetriggering event includes one or more of: i) a change to a data record;or ii) a change to pre-programmed element. In some embodiments, eachpre-programmed element is fully executable without being directlydependent upon the execution of any other pre-programmed element. Insome embodiments, a failure of one instance of one of the pre-programmedelements does not prevent the execution and completion of anotherinstance of the same pre-programmed element. In some embodiments, theinstance of the exemplary routine reaches a successful conclusion if allof the pre-programmed elements within the instance of the exemplaryroutine are completed.

In some embodiments, the method further includes creating one or moreadditional instances of the exemplary routine, and completing, withoutintervention, an execution of all of the one or more additionalinstances of the exemplary routine after detecting an error in theinstance of the exemplary routine that prevents the completion of theexemplary routine. In some embodiments, the method further includesafter receiving the intervention to complete the at least one instanceof the pre-programmed element, and decrementing a retry field tocomplete execution of the instance of the exemplary routine. In someembodiments, the occurrence of an error that prevents the completion ofthe instance of the exemplary routine without intervention does notprevent the completion of the one or more additional instances of theexemplary routine.

BRIEF DESCRIPTION OF THE SEVERAL VIEWS OF THE DRAWINGS

The following detailed description of embodiments of the system andmethod for modular construction of executable programs havingself-contained program elements, will be better understood when read inconjunction with the appended drawings of an exemplary embodiment. Itshould be understood, however, that the invention is not limited to theprecise arrangements and instrumentalities shown.

In the drawings:

FIG. 1 is a block diagram illustrating an implementation of a processsynchronization system, in accordance with an exemplary embodiment ofthe present disclosure.

FIG. 2A is an entity relationship diagram illustrating an implementationof the database of FIG. 1 .

FIG. 2B is an example of a reaction table according to the entityrelationship diagram in FIG. 2A.

FIG. 3 illustrates an exemplary flow chart for a method of creating anexemplary routine in accordance with an embodiment of the presentdisclosure

FIG. 4 illustrates an exemplary flow chart for a method of creating aninstance of an exemplary routine in accordance with an embodiment of thepresent disclosure.

FIG. 5 illustrates an exemplary flow chart for a method of executinginstances of pre-programmed elements in accordance with an embodiment ofthe present disclosure.

FIGS. 6A-6B illustrates an exemplary user interface for the creation ofa new exemplary routine, in accordance with an exemplary embodiment ofthe present disclosure.

FIG. 6C illustrates an example of computer executable code associatedwith a pre-programmed element.

FIGS. 6D-6H illustrate an example of an administrator user interface forthe creation of a new exemplary routine, in accordance with an exemplaryembodiment of the present disclosure.

FIG. 6I illustrates an example of a customer service user interface inaccordance with an exemplary embodiment of the present disclosure.

FIG. 7 illustrates an exemplary flowchart for a method of execution ofan instance of an exemplary routine, in accordance with an exemplaryembodiment of the present disclosure.

FIG. 8 illustrates an exemplary flowchart for a method of execution ofan instance of an instance of an exemplary routine where apre-programmed element fails to execute, in accordance with an exemplaryembodiment of the present disclosure.

FIG. 9 illustrates an exemplary flowchart for a method of execution ofan instance of an instance of an exemplary routine where apre-programmed element permanently fails to execute, in accordance withan exemplary embodiment of the present disclosure.

FIG. 10 illustrates an exemplary flowchart for a method of execution ofan instance of an exemplary routine with a long-running pre-programmedelement, in accordance with an exemplary embodiment of the presentdisclosure.

FIG. 11 illustrates an exemplary flowchart for a method of execution ofan instance of an exemplary routine where the exemplary routine isupdated mid-execution, in accordance with an exemplary embodiment of thepresent disclosure.

FIG. 12 illustrates an exemplary flowchart for a method of execution ofan instance of an exemplary routine where underlying records aremodified mid-execution, in accordance with an embodiment of the presentdisclosure.

FIG. 13 illustrates an exemplary flowchart for a method of execution ofan instance of an exemplary routine when underlying records are modifiedmid-execution, in accordance with another embodiment of the presentdisclosure.

FIG. 14 illustrates an exemplary flowchart for a method of performing afault tolerant automated sequence of computer implemented tasks, inaccordance with an exemplary embodiment of the present disclosure.

DETAILED DESCRIPTION

Numerous details are described herein in order to provide a thoroughunderstanding of the example embodiments illustrated in the accompanyingdrawings. However, some embodiments may be practiced without any of thespecific details, and the scope of the claims is only limited by thosefeatures and aspects specifically recited in the claims. Furthermore,well-known methods, components, and circuits have not been described inexhaustive detail so as not to unnecessarily obscure pertinent aspectsof the embodiments described herein.

Some embodiments of the present disclosure provide improvements togenerating automated tasks by providing a modular processsynchronization system configured to efficiently develop and executeprograms having self-contained program elements. The system may beconfigured to execute and monitor the automated process synchronizationprograms via two or more servers in communication over a network.Referring to the drawings in detail, wherein like reference numeralsindicate like elements throughout, there is shown in FIGS. 1-2 a systemfor modular construction of executable programs having self-containedprogram elements, in accordance with an exemplary embodiment of thepresent disclosure.

In one embodiment, the system for modular construction of executableprograms having self-contained program elements 100 includes one or morecomputers having one or more processors and memory (e.g., one or morenonvolatile storage devices). In some embodiments, memory or computerreadable storage medium of memory stores programs, modules and datastructures, or a subset thereof for a processor to control and run thevarious systems and methods disclosed herein. In one embodiment, anon-transitory computer readable storage medium having stored thereoncomputer-executable instructions which, when executed by a processor,performs one or more or any combination of the methods or stepsdisclosed herein.

Referring to FIG. 1 , there is shown a block diagram illustrating animplementation of a system for modular construction of executableprograms having self-contained program elements, generally designated100. While some example features are illustrated, various other featureshave not been illustrated for the sake of brevity and so as not toobscure pertinent aspects of the example embodiments disclosed herein.To that end, as a non-limiting example, the system for modularconstruction of process synchronization programs 100, referred to hereinas system 100, may include one or more networked servers. The one ormore networked servers may share any number of logical units. In someembodiments, the one or more networked servers are assigned discretetasks. For purposes of explaining the invention, reference may be madeto a particular server with a particular function. It should beunderstood that the particular function may be unique to the server orthe functionality may be shared by multiple servers.

In one embodiment, system 100 comprises a processing server 102, amonitoring server 104, a worker system 106, one or more client devices108, and one or more databases 110. The system may further include anoptical character recognition (OCR) server 112, one or more veterinarianservers 114, one or more storefront servers 107, and one or morecustomer devices 116. In one embodiment, the functionality of theprocessing server 102, monitoring server 104 and worker server 106 isshared by one server or across one or more networked severs. In oneembodiment, the functionality of each of the processing server 102,monitoring server 104 and worker server 106 are performed by one moreservers that do not overlap in functionality. For example, the one ormore servers that provide functionality for the processing server 102may be different from the one or more servers that provide thefunctionality of monitoring server 104.

The processing server 102 may be one or more computing servers thatprovide secure access to a plurality of pre-programmed elements(sometimes referred to herein as “atoms”), one or more of which may becombined into an exemplary routine (sometimes referred to herein as“reactions”). The processing server 102 may be configured to display anadministrator facing user interface (“UI”), also referred to as an adminUI, which allows users (e.g., administrators 118, developers 120) todefine exemplary routines, and/or request/create new pre-programmedelements. Administrators 118 may be users with little to no computerprogramming knowledge (e.g., customer service representatives or usershaving little to no skill in the art of computer programming).Developers 120 may be users with computer programming knowledgenecessary to write computer programs which become the pre-programmedelements (e.g., software engineers or users having at least ordinaryskill in the art of computer programming). Administrators 118 anddevelopers 120 may access the processing server 102 via client devices108. Client devices 108 may be operated on any suitable computer device,such as a computer, a laptop computer, a tablet device, a netbook, aninternet kiosk, a personal digital assistant, a mobile phone, a smartphone, a gaming device, a computer server, or any other computingdevice. The processing server 102 may be configured to generate theadmin UI such that it is accessible via the internet and viewable by adeveloper 120 and/or administrator 118 on a respective client device108.

The processing server 102 may be configured to communicate with one ormore servers (e.g., storefront server 107) configured to generate acustomer facing UI such that it is accessible via the internet andviewable by a customer on a respective customer device 116. The customerdevice 116 may be operated on any suitable computer device, such as acomputer, a laptop computer, a tablet device, a netbook, an internetkiosk, a personal digital assistant, a mobile phone, a smart phone, agaming device, a computer server, or any other computing device. Thecustomer facing UI may be configured to allow one or more customers toview and select products for purchase. The products for purchase mayhave associated data stored in a database in communication with thestorefront server 107. In some embodiments, storefront server 107 is incommunication with database 110 that stores product data associated withthe products for purchase. One or more of the products displayed on thecustomer facing UI may require authorization in order for a customer topurchase them. For example, a product may be a prescription tickmedication for a dog that requires authorization from a veterinarian.The database 110 may store a record indicating whether there is anauthorization for a user to purchase a specific product displayed on thecustomer facing UI. The processing server 102 and/or storefront server107 may be configured to query database 110 to determine if aprescription authorization for the requested product exists. Thedatabase may store customer information such as: customer name, address,phone number, pet information, veterinary clinics associated with thepets owned by the customer, and prescription information.

The processing server 102 may be configured to communicate with one ormore databases (e.g., database 110) to receive and transmit datarelating to pre-programmed elements, and/or exemplary routines. Database110 may include a relational database (see FIG. 2 ). In someembodiments, database 110 may include a non-relational database.Database 110 may store data related to a plurality of pre-programmedelements. A pre-programmed element may be an element of computerexecutable code written by a programmer (e.g., developer 120, softwareengineer, computer scientist). A pre-programmed element may be anindependently executable self-contained unit of computer code configuredto perform a specific task (e.g., send email to customer, process orderrefund, cancel order shipping). Independently executable refers to theconfiguration of each pre-programmed element to complete executionwithout requiring an output from any other pre-programmed element whichhas executed so long as any data objects required for the pre-programmedelement are known. The data related to the pre-programmed elements mayinclude a unique identifier which identifies each pre-programmedelement, and the executable self-contained unit of computer code.

The database 110 may store data related to exemplary routines associatedwith one or more pre-programmed elements that correspond to tasksrequired to accomplish a certain objective. An exemplary routine may bea grouping of pre-programmed elements having a sequence that defines theorder in which the pre-programmed elements execute. For example, anobjective may be to process the termination of and cancel a pendingorder for a product that was placed through a customer portal. To fullyprocess the termination of a pending order the system 100 may implementtasks for: communication related to the customer account associated withthe order, rigorous financial processing steps, shipping notices andinventory management. Specific automated tasks may include: transmissionof electronic notification related to customer account that the orderhas been cancelled, processing of refund request associated with thecustomer account, termination of shipping order and, if necessary,returning a product to inventory or indicating in an inventory trackingsystem that the product is available for sale in connection with a neworder. In this example, the exemplary routine would includepre-programmed elements that have executable code capable of handlingthe above-mentioned tasks and define the order in which thepre-programmed elements are executed. Further to this example, thesequence of execution may be to cancel shipping of the product to thecustomer, process a refund to the customer, and email the customer anotification that the order cancellation has been processed. It will beunderstood though, that exemplary routines may include differentpre-programmed elements and/or define different sequences of executionfor the pre-programmed elements.

The pre-programmed elements may be associated with one or more exemplaryroutines. For example, the send email pre-programmed element may beincluded in a plurality of different exemplary routines (e.g., ordercancellation requests, requests for additional customer information,notifications for a change in quantity of an ordered product). Datastored in database 110 relating to an exemplary routine may include aunique identifier for the exemplary routine, the sequence in whichpre-programmed elements are to be executed, and a listing of thepre-programmed elements that are included in the exemplary routine. Insome instances, an exemplary routine may include two or more of the samepre-programmed elements. For example, an exemplary routine X may includepre-programmed elements A, B, and C and include A, B, C, A as the orderof execution. In some instances, an exemplary routine may include two ormore pre-programmed elements having the same sequence value. Forexample, an exemplary routine may include pre-programmed elements A, B,C, and D and a sequence that defines the order of execution to be A,then BC, then D where element A executes, then elements B and C executein parallel (e.g., initiating at the same time or approximately the sametime or overlapping execution), then element D executes.

The database 110 may also store data required for execution of one ormore of the pre-programmed elements. The database 110 may store dataassociated with customer records, customer interactions, and/or clinics(e.g., veterinary clinics, veterinarians). Customer record data mayinclude data relating to the customer and/or an account owned by thecustomer and stored in database 110 (e.g., unique customer ID, customername, email address, phone number, shipping address, and pet(s) owned bythe customer). Customer interaction data may include data relating toone or more interactions of the customer with the storefront server 107(e.g., unique identifiers associated with orders for products placed bythe customer, products ordered by the customer, shipping address,payment method, order quantity, order status, payment status, andshipping method). Clinic data may include data relating to one or moreclinics associated with a customer, processing server 102, and/orstorefront server 103 (e.g., a veterinarian associated with a customer’spet, the veterinarians contact information, and the veterinarian’sveterinary clinic). Depending on the pre-programmed element, some ofsaid data may be required to execute said pre-programmed element. Forexample, a pre-programmed element configured to email a customer with anotification may require customer records to determine the customer’semail address. Similarly, a pre-programmed element configured to refundpayment of a cancelled order may require data associated with an ordernumber and payment method. It will be understood that the database 110,or another database in communication with database 110 and/or processingserver 102 may store data required for execution of the pre-programmedelements.

The processing server 102 may be configured to receive a request forexecution of one or more pre-programmed elements. The request forexecution of one or more pre-programmed elements may be in response toan event, or occurrence, for which a resolution is sought. The event maybe referred to as a triggering event or an incident herein. For example,an incident may be a customer requesting cancellation of an order. Inorder to resolve the customer’s order cancellation incident, one or moretasks may be executed, preferably in a certain order, in order toresolve the order cancellation incident. The one or more tasks maycorrespond to one or more of the pre-programmed elements which may beincluded in an exemplary routine. The request for execution of the oneor more pre-programmed elements may include an indication as to theexemplary routine associated with the one or more pre-programmedelements. The processing server 102 may transmit the request forexecution of the one or more pre-programmed elements in response to aninput from an administrator 118 and/or a developer 120. The input fromthe administrator 118 and/or developer 120 may be received on anassociated client device 108 displaying the admin UI. For example, anadministrator 118 may receive communication (e.g., email, phone call, amessage through an online communication platform) from a customer thatwishes to cancel an order. The administrator 118 may, via a clientdevice 108, access the processing server 102 which transmits the adminUI for display on client device 108. The administrator 118 may then,after locating the order in which the user wishes to cancel, provide aninput, via the client device 108, at a displayed icon on the admin UI tocancel the order (e.g., a ‘cancel order’ button). Additionalnon-limiting examples of incidents which trigger execution of one ormore pre-programmed elements may include a request by a veterinaryclinic to switch from paper (e.g., fax) notifications to electronicnotifications (e.g., email), a request to email all veterinariansassociated with a specific veterinary clinic the number of pendingprescriptions for their review, and a notification sent to a customer toverify a duplicate order to ensure the duplicate order was notaccidental.

The processing server 102 may be configured to communicate with database110 to create and store instances of one or more exemplary routinesand/or one or more instances of pre-programmed elements for whichexecution is requested. An instance of an exemplary routine (sometimesreferred to as a “molecule” herein) may refer to a version of theexemplary routine stored in database 110. In one embodiment, the versionof the exemplary routine that makes up the instance is based on theconfiguration of the exemplary routine at the time the instance wascreated. That version of the exemplary routine may differ from a latercreated instance of the exemplary routine. For example, an aspect of oneof the pre-programmed elements may be changed between the creation of afirst instance and a second instance of the same exemplary routine,where the second instance is created later than the first instance. Inone embodiment both instances (e.g., the first and second instance) ofthe exemplary routine are stored in the database and may be executedaccording to their respective configurations at the time they werecreated. In some embodiments, the aspect of the exemplary routine thatis changed includes one or more of: i) the substitution of onepre-programmed element for another pre-programmed element; ii) theaddition of a pre-programmed element; iii) the elimination of apre-programmed element; iv) a change to the sequence of performance ofthe pre-programmed element; v) a new sequence for a new set ofpre-programmed elements; or vi) a combination of two or more of theforegoing.

In one embodiment, a first instance of an exemplary routine X is createdat a time T1 and may correspond to the configuration of the exemplaryroutine X at time T1. Exemplary routine X may be modified at a secondtime T2 after T1 such that a pre-programmed element is added or removedfrom the exemplary routine. A second instance of exemplary routine X iscreated on or after the second time T2 and may include the configurationcorresponding to the modification made at T2. Both the first instanceand second instance of exemplary routine X may be stored in database 110for processing while the first instance represents the configuration ofexemplary routine X at time T1 and the second instance represents theconfiguration of exemplary routine X after modification (e.g. on orafter time T2). The configuration of an exemplary routine at the time aninstance is created may include data such as an identifier for theexemplary routine (e.g., a name for the exemplary routine, a uniqueidentifier), a listing of pre-programmed elements included in theexemplary routine, and the sequence of execution for the pre-programmedelements.

In some embodiments, the instance of the exemplary routine includes aversion of the exemplary routine that includes one or more pointers toexecutable code (e.g., executable code associated with pre-programmedelements included in the exemplary routine). In some embodiments, theinstance of the exemplary routine contains no executable code andincludes, instead, pointers to executable code. In one embodiment, whenthe code associated with a pre-programmed element is updated anyinstance of an exemplary routine that has not yet run, will execute fromthe updated code when the instance is executed. In one alternativeembodiment, the instance of the exemplary routine includes executablecode that does not execute via a pointer and does not therefore runupdated code if a relevant pre-programmed element is updated after theinstance is created.

In one embodiment, database 110 may store exemplary routines andinstances of exemplary routines. For example, database 110 may store anexemplary routine X which is for handling an order cancellation request.The database 110 may store a configuration of exemplary routine X (e.g.,data relating to the exemplary routine). The configuration may include aunique identifier for the exemplary routine, pre-programmed elementsincluded in the exemplary routine as they exist at the time the instanceis created, and the associated sequence of execution as that sequence isdefined at the time the instance is created. In some embodiments, aninstance of the exemplary routine is a version of the exemplary routinewhich may be stored as a record in database 110 separate from theexemplary routine to which it corresponds. For example, exemplaryroutine X is stored separately from the instance of exemplary routine Xin database 110. There may be a plurality of instances of exemplaryroutines stored in database 110. For example, in some instances theremay be two or more instances of exemplary routine X stored in database110 and one or more instances of different exemplary routines stored indatabase 110. In some embodiments, there may be ten or more, fifty ormore, one hundred or more, or more than a hundred instances of exemplaryroutines stored in database 110. Instances of exemplary routines storedin database 110 may include multiple instances of the same exemplaryroutine, instances of different exemplary routines, or any combinationthereof.

An instance of one or more pre-programmed elements may refer to a copyof the data corresponding to the pre-programmed element stored indatabase 110. For example, database 110 may store a pre-programmedelement A that is for sending an email notification. The data associatedwith pre-programmed element A includes the unique identifier and apointer to the computer code to be executed. An instance ofpre-programmed element A is a copy of said data including the uniqueidentifier and a pointer to the computer code to be executedcorresponding to pre-programmed element A. The instance of thepre-programmed element may be stored as a record in database 110,separate from the pre-programmed element it corresponds to. For example,pre-programmed element A is stored separately from the instance ofpre-programmed element A in database 110. There may be a plurality ofinstances of a pre-programmed element stored in database 110. Forexample, in some embodiments, there may be two or more instances ofpre-programmed element A stored in database 110. In some embodiments,there may be ten or more, fifty or more, one hundred or more, or morethan a hundred instances of the same pre-programmed element stored indatabase 110. In some embodiments, two or more databases are used tostore pre-programmed elements and instances of the pre-programmedelements respectively. Database 110 may include an elements database122, routines database 124 and instances database 126. The elementsdatabase 122 may be configured to store the pre-programmed elementscreated as described above. The routines database 126 may be configuredto store the exemplary routines created as described above. Theinstances database 128 may be configured to store instances ofpre-programmed elements, and exemplary routines created as describedabove. An instance of an exemplary routine and/or an instance of apre-programmed element may be a version of the exemplary routine and/orpre-programmed element that is applicable at the point in time in whichthe instance was created.

The processing server 102 may be configured to create an entry indatabase 110 for an instance of an exemplary routine for which executionis requested. The processing server 102 may include executable code,that when executed, causes the database 110 to create one or more rowsincluding data for the instance of the exemplary routine, and instancesof the pre-programmed elements included in the exemplary routine. Theprocessing server 102 may be configured to cause database 110 to createdata entries for data related to the incident which triggered thecreation of the instance of the exemplary routine and/or data entriesrequired for execution of instances of pre-programmed elements. Forexample, database 110 may store, for each instance of an exemplaryroutine, incident data which may correspond to data for a customerinteraction record, contact data corresponding to customer and/orveterinarian contact records, and/or org data corresponding toveterinarian clinic records, shelter records, or the like.

Referring to FIG. 2A, there is shown an entity relationship (ER) diagramfor database 110 in accordance with an exemplary embodiment of theinvention. The ER diagram in FIG. 2 may relate to how instances ofexemplary routines are associated with corresponding exemplary routines,instances of pre-programmed elements, incident data, and other datarequired for the execution of the instance of the exemplary routine.Database 110 may store data associated with incidents, contacts, orgs,pre-programmed elements, exemplary routines, and instances of exemplaryroutines in one or more tables. The database 110 may include an incidenttable, contact table, and org table for storing data associated withincidents, contacts, and organizations respectively. Database 110 mayinclude an atom table, atom state menu table, and atom type table forstoring data related to pre-programmed elements. Database 110 mayinclude a molecule and molecule type menu tables for storing datarelated to instances of exemplary routines. Database 110 may include areactions table for storing data related to exemplary routines.

Data associated with an instance of a pre-programmed element mayinclude: a unique ID, incident, contact, org, state, retry count, name,molecule, notes, and/or sequence number data entries. The unique ID maybe a unique identifier which is specific to the instance of thepre-programmed element. The incident entry may be an optional foreignkey that links the instance of the pre-programmed element and theincident which triggered creation of the instance of the exemplaryroutine stored in a separate table in database 110. The contact entrymay be an optional foreign key that links the instance of thepre-programmed element to customer and/or veterinarian informationstored in a separate table on database 110. The org entry may be anoptional foreign key that links the instance of the pre-programmedelement to veterinarian clinic, shelter information stored in a separatetable on database 110. The state entry may include an indication of thestatus (e.g., the state) of the pre-programmed element (e.g., pending,cancelled, failed, completed, locked). The state may be an integer valueindicating the status of the instance of the pre-programmed element(e.g., 0 = pending, 1= cancelled, 2=failed, 3=complete, 4=locked). Thestate may alternatively be a text value corresponding to the status ofthe pre-programmed element. The retry count entry may correspond to anumber of times execution of an instance of the pre-programmed elementhas been attempted as discussed in more detail below. The name entry maybe a human readable name of the pre-programmed element and may be aforeign key that links the instance of the pre-programmed element to thecorresponding pre-programmed element stored in a separate table indatabase 110. The molecule entry may be a foreign key that links theinstance of the pre-programmed element to the corresponding instance ofthe exemplary routine. The notes entry may be a free form field that maybe used to store structured data required for execution. For example,the notes entry may include a JSON formatting array storing one or moreidentifiers required for execution of one or more pre-programmedelements. The sequence number entry may correspond to a sequence numberfor the instance of the pre-programmed element that is copied from theexemplary routine during creation of the instance of the exemplaryroutine. Sequence numbers created in this manner and stored as a dataentry in the instance of the pre-programmed element may allow executionof the pre-programmed element as defined by the exemplary routine at thetime the instance of the exemplary routine is created. Put another way,by storing the sequence number during creation of an instance of theexemplary routine, the pre-programmed element will execute according tothe sequence defined by the exemplary routine even if the exemplaryroutine is modified during execution of the instance of the exemplaryroutine, as described in more detail below.

Database 110 may include one or more tables for storing informationrelated to instances of the exemplary routines. Data associated withinstances of exemplary routines may include a unique identifier, a type,and notes data entries. The unique identifier may be a private key thatis unique to the instance of the exemplary routine and may link theinstance of the exemplary routine to instances of correspondingpre-programmed elements (e.g., the unique identifier data entry andmolecule data entry). The type data entry may be a foreign key thatdefines a many-to-many relationship between the instance of theexemplary routine and the exemplary routine. The many-to-manyrelationship may be established via a table (e.g., the MoleculeTypeMenu) that links the table storing data for the instance of theexemplary routine and the table storing data for the exemplary routine.The notes data entry may be a free form field to store data. In someembodiments, notes data in the molecule table includes structured datathat is required or useful for some implementations.

Database 110 may include one or more tables (e.g., the reaction table)for storing information related to exemplary routines. Data associatedwith exemplary routines may include a unique identifier, required atomtype, sequence number, require incident, require contact, require org,and/or molecule name data entries. The unique identifier may be aprivate key which is unique to the exemplary routine. The required atomtype data entry may be a foreign key corresponding to one or morepre-programmed elements required for execution. The sequence number dataentry may include the order of the execution for the pre-programmedelements included in the exemplary routine. The require incident dataentry may include an indication as to whether incident information mustbe present in database 110 for execution of the instance of apre-programmed element included in the exemplary routine. In oneexemplary embodiment, the require incident data entry may be specific toan instance of a pre-programmed element. For example, the requireincident data entry may be “yes” for an instance of pre-programmedelement A and “no” for an instance of pre-programmed element B. Inanother exemplary embodiment, the require incident data entry may not bespecific to an instance of a pre-programmed element. The require contactdata entry may include an indication as to whether contact informationmust be present in database 110 for execution of the instance of apre-programmed element included in the exemplary routine. In oneexemplary embodiment, the require contact data entry is specific to aninstance of a pre-programmed element. In another exemplary routine, therequire contact data entry is not specific to an instance of apre-programmed element. The require org data entry may include anindication as to whether organization data (e.g., veterinary clinicdata, shelter data) must be present in database 110 for execution of theinstance of a pre-programmed element included in the exemplary routine.In one exemplary embodiment, the require org data entry may be specificto an instance of a pre-programmed element. In another exemplaryembodiment, the require org data entry may not be specific to aninstance of a pre-programmed element. The molecule name data entry maybe a foreign key which defines the instance of the exemplary routinethat a pre-programmed element will be included in.

Referring to FIG. 2B there is shown an example of a reaction tablestoring information related to an exemplary routine“cancelpetscriptionrelease”. Each row in this example reaction tablecorresponds to a pre-programmed element included in the exemplaryroutine and/or an instance of the pre-programmed elements included in aninstance of the exemplary routine. The reaction table shown hereincludes the pre-programmed elements and corresponding sequences definedby the exemplary routine. In this example, the exemplary routineincludes four pre-programmed elements: “cancelpetscriptionrelease”,“cancelpetscriptionreleasesendemail”, and two “orgisDigital”pre-programmed elements. Each pre-programmed element may include aunique ID associated with pre-programmed element. In some embodimentsthe unique ID is associated with an instance of the pre-programmedelement (e.g., ID values 16 and 17 correspond to different instances ofpre-programmed element “orgsIsDigital”). Each pre-programmed element mayinclude an indication of what information is required in order for thepre-programmed element to execute. For example, pre-programmed element“cancelpetscriptionrelease” requires incident information but does notrequire contact or organizational information in order to execute. Eachpre-programmed element may include a sequence data associated with thesequence of execution as defined by the exemplary routine. For example,“petscriptionrelease” and one instance of “orgsIsDigital” have asequence value of 1 indicating that instances of these twopre-programmed elements should be executed in parallel. It will beunderstood that the reaction table shown in FIG. 2B is an example andthat in practice the reaction table may store a plurality of entriesassociated with different instances of exemplary routines each includingone or more instances of pre-programmed elements.

The database 110 may store a table associated with the type ofpre-programmed element (e.g., the AtomType Menu in FIG. 2 ) for relatingan instance of a pre-programmed element with the executable code for thecorresponding pre-programmed element. In some embodiments, storing theexecutable code for a pre-programmed element separate from the instanceof said pre-programmed element may allow the system 102 to maintainreferential integrity within database 110. In some embodiments, storingthe executable code for the pre-programmed element separate from theinstance of said pre-programmed element may allow an exemplary routineto be modified without affecting an instance of said exemplary routinewhich is currently being executed.

The database 110 may store a plurality of instances of differentpre-programmed elements. For example, the database 110 may store arecord of three instances of pre-programmed element A, five records ofpre-programmed element B, and 10 records of pre-programmed element C. Itwill be understood that the database 110 may store any number orcombination of instances of pre-programmed elements. The database 110may include a record of all pre-programmed elements with a pendingstatus.

The processing server 102 may be configured to transmit a request todatabase 110 to create and store an instance of each pre-programmedelement in an exemplary routine in database 110. The request fromprocessing server 102 to database 110 to store said instances may be inresponse to an input and/or request received from a client device 108.The input and/or request from client device 108 may correspond to aninput from an administrator 118 or developer 120 who wishes to causesystem 100 to perform a series of tasks. For example, an administrator118 may provide an input on client device 108 that is displaying anadmin UIto request cancellation of an order for a product (e.g., a pressof a button displayed on admin UI corresponding to cancelling an order).The order cancellation input may cause processing server 102 to transmita request to database 110 to create an instance of each pre-programmedelement included in an exemplary routine for order cancellation. Asdescribed above, this exemplary routine may include pre-programmedelements for email notifications, a refund of the currency to a customerthat placed the order, and a cancellation of any pending shipment of theproduct to the customer. In this example, an instance of each of thesepre-programmed elements is created and stored in database 110 forexecution. Each instance of pre-programmed elements included in theexemplary routine may initially be stored in database 110 with a pendingstatus indicator.

The processing server 102 and monitoring server 104 may be configured todetermine the order in which instances of pending pre-programmedelements should be executed and/or to execute said instances. Themonitoring server 104 may be configured to transmit a request for a listof all pending instances of pre-programmed elements to processing server102. The processing server 102 may be configured to determine, based onthe data associated with instances of the pre-programmed elements, theorder in which the pre-programmed elements should be executed. Forexample, the processing server 102 may be configured to determine thatan instance of pre-programmed element B should not be executed until aninstance of pre-programmed element A is executed. The processing server102 may be configured to determine the order in which instances ofpre-programmed elements are to be executed as defined by an instance ofthe exemplary routine. For example, an instance of a first exemplaryroutine may include instances of pre-programmed elements A-D having adefined sequence (e.g., element A executes before element B thatexecutes before element C that executes before element D). For example,an instance of an exemplary routine may have three instances ofpre-programmed elements which have not executed and the processingserver 102 may determine which of those instances needs to be executednext as defined by the sequence.

The processing server 102 may be configured to determine a portion ofinstances of pre-programmed elements for execution from the record ofall pending pre-programmed elements stored in database 110. For example,database 110 may have stored, at a point in time, one hundred instancesof pre-programmed elements having a pending status. The processingserver 102 may determine that twenty of the one hundred instances ofpre-programmed elements need to be executed. The processing server 102may determine the portion of pre-programmed elements for execution basedon corresponding instances of exemplary routines. For example, ifdatabase 110 has stored therein one hundred instances of pre-programmedelements, those instances may correspond to twenty instances ofexemplary routines. Each instance an of exemplary routine including thesequence of execution for corresponding instances of pre-programmedelements which are stored in database 110. The processing server 102 maydetermine where in the sequence of execution, each instance of anexemplary routine is currently at (e.g., a first exemplary routine hasnot started, a second exemplary routine has executed the second instanceof a pre-programmed element in its sequence). Based on the currentsequence of execution, the processing server 102 may determine whichinstances of pre-programmed elements need to be executed next. Forexample, if there are twenty instances of exemplary routines, eachincluding five instances of pre-programmed elements, none of which havebeen executed yet, the processing server 102 is configured to determinethat the instance of a pre-programmed element corresponding to the firstpre-programmed element in the sequence defined by the correspondinginstance of the exemplary routine needs to be executed.

In one embodiment, system 100 also includes logical units (LUs) thatincludes one or more of a monitor LU, a processor LU and a worker LU. Inone embodiment, the monitor LU is a logical unit that initiatesexecutions and monitors progress of various activities on system 100.For example, the monitor LU may include an AWS Step-Function, an AWSLambda, and/or associated monitoring and alerting. In one embodiment,the processor LU includes several code-classes used to i) collect dataon pending executions, ii) execute pending tasks, iii) communicateinformation back to the monitor unit and iv) combinations thereof. Theprocessor LU may include files (such as plain-text files) that may beexecuted by one or more of the servers for rendering on a browser. Insome embodiments, the monitor LU includes a cron_runner functionconfigured to request pending instances of pre-programmed elements andreceive requests for execution of instances of pre-programmed elements.In some embodiments, the monitor LU includes a parallel_process_atomsfunction configured to handle the execution of code corresponding to thepre-programmed elements as well as retrieve a list of pending instancesof pre-programmed elements to be executed. In some embodiments, theprocessing LU includes a molecule_utilities function configured tocreate entries in database 110 for new pre-programmed elements andcancel pending instances of exemplary routines. In an exemplary routine,the molecule_utilities functions is configured to handle all entries anddeletions from database 110 relating to exemplary routines,pre-programmed elements, and/or instances thereof. In one embodiment,the worker LU includes a body of code used to complete the actionsdefined for a requested pre-programmed element. For example, the workerLU may include code for completing actions defined by pre-programmedelements such as: processsendorgstatustokyrios, clinicprefupdateatom andprocesscancelRxOrderInPetcriptions. In one embodiment, the worker LUincludes one or more private methods within the one or more files of theprocessor LU and can call out to other functions or classes.

In some embodiments, each of the monitor LU, processor LU and worker LUare associated with and executed by a dedicated server. In someembodiments, one or more servers are configured to execute one or moreof the LUs. In other embodiments, the LUs are shared across two or moreservers. The monitoring server 104 may be one or more computing serversthat are configured to initiate the execution of and monitor the statusof instances of pre-programmed elements. The monitoring server 104 maybe configured to communicate with database 110 to request and receive arecord of all pending pre-programmed elements for which execution isrequested. The monitoring server 104 may be configured to request therecord of all pending pre-programmed elements at a pre-defined interval.In some embodiments, the pre-defined interval is one minute. In someembodiments, the pre-defined interval is about 30 seconds, about 60seconds, about 90 seconds, about 120 seconds, about 150 seconds or about180 seconds.

The processing server 102 may create a list of all instances ofpre-programmed elements to be executed next in sequences defined by theinstances of exemplary routines and transmit the list to the monitoringserver 104. The monitoring server 104 may be configured to assign, basedon the list received from the processing server 102, instances ofpre-programmed elements to one or more sets of instances ofpre-programmed elements for parallel execution. For example, themonitoring server 104 may receive a list of a thousand instances ofpre-programmed elements from processing server 102. The monitoringserver 104 may then determine that one set for parallel execution mayinclude ten instances of the thousand instances received and another setmay include twenty instances and so on. The monitoring server 104 may beconfigured to initiate execution of one or more instances pre-programmedelements. The monitoring server 104 may be configured to initiateexecution of one or more instances pre-programmed elements identifiedfor execution by processing server 102, as described above. Themonitoring server 104 may be configured to iterate through thedetermined sets for parallel execution and transmit said sets to theprocessing server 102 to initiate execution of the instances ofpre-programmed elements included in said set. For example, themonitoring server 104 may, after determining the sets for parallelexecution, transmit the sets to the processing server 102 for execution.In this manner, the monitoring server 104 may initiate execution ofinstances of pre-programmed elements and the processing server 102 mayperform the execution of the instances. In one exemplary embodiment,each iteration through the determined sets may correspond to apredetermined interval (e.g., interval defined in step 502 of method 500discussed below). In other embodiments, the monitoring server 104 isconfigured to iterate through the determined sets for parallelexecution, initiate execution of the instances of pre-programmedelements and perform execution of the instances.

As mentioned above, the monitoring server 104 may be configured toinitiate execution of instances of two or more pre-programmed elementsin parallel. The two or more instances pre-programmed elements may betwo or more instances of the same pre-programmed element. For example,the two or more instances of pre-programmed elements may be two or moreinstances of pre-programmed element A. In some embodiments, the two ormore instances of pre-programmed elements may be two or more instancesof different pre-programmed elements. For example, the two or moreinstances of pre-programmed elements may be an instance ofpre-programmed element A and an instance of pre-programmed element B. Insome embodiments, the two or more instances of pre-programmed elementsmay be a combination of instances of the same pre-programmed elementsand different pre-programmed elements. For example, the two or moreinstances may be two instances of pre-programmed element A, an instanceof pre-programmed element B, and two instances of pre-programmed elementC. The instances of two or more pre-programmed elements executed inparallel may be associated with different instances of exemplaryroutines. For example, an instance of element A may be associated withan instance of a first exemplary routine and an instance of element Bmay be associated with an instance of a second exemplary routine.

The processing server 102 may be configured to monitor whether aninstance of a pre-programmed element fails to execute. For example, theprocessing server 102 may monitor the execution of an instance ofpre-programmed element A and determine that the instance ofpre-programmed element A failed or succeeded to execute. In the eventthat an instance of a pre-programmed element fails to execute, theprocessing server 102 may be configured to retry execution of the failedinstance of the pre-programmed element. The processing server 102 may beconfigured to retry execution of an instance of a pre-programmed elementa predetermined number of times before ceasing to retry execution of theinstance of the pre-programmed element. The processing server 102 may beconfigured to retry execution one time, two times, three times, fourtimes, five times, six times, seven times, or more than seven timesbefore ceasing to proceed to another retry.

The monitoring server 104 may be configured to validate that executionof instances of pre-programmed elements do not proceed past apredetermined time threshold, that the processing server 102 does notbecome unresponsive, and/or that a predetermined number of instances ofpre-programmed elements are executed in parallel. The monitoring server104 may be configured to transmit an alert notification to anadministrator 118 and/or developer 120 if the processing server 102becomes unresponsive. The monitoring server 104 may be configured tomonitor the amount of time that an instance of a pre-programmed elementis taking to execute. For example, the monitoring server 104 may beconfigured to determine that an instance of pre-programmed element A hastaken a minute to execute. The monitoring server 104 may be configuredto be in communication with processing server 102 to transmitinformation corresponding to the status of instances of pre-programmedelements. The monitoring server 104 may transmit to the processingserver 102 a list of the instances of pre-programmed elements which havefailed to execute, have succeeded to execute, and/or that are currentlyexecuting.

The processing server 102 may be configured to monitor the monitoringserver 104 to monitor instances of pre-programmed elements that arebeing executed and monitor any buildup of pending instances ofpre-programmed elements that need to be executed. In this manner, thefunctionality of the system 100 described herein is split between atleast two servers (e.g., processing server 102 and monitoring server104). In one embodiment, splitting functionality between processingserver 102 and monitoring server 104 enables redundant monitoringfunctionality such that processing server 102 may monitor monitoringserver 104 and vise versa to identify whether there is a server failureat either the processing server 102 or monitoring server 104 (e.g.,failure to execute pre-programmed elements, network connection issues).In the event instances of pre-programmed elements are not fullyexecuted, corrective action may be taken to ensure errors in executionof pre-programmed elements does not cause a halt in execution of otherinstances of pre-programmed elements.

The processing server 102 may include a worker system 106 which may beconfigured to execute instances of pre-programmed elements. For example,worker system 106 may include a collection of computer executable code(e.g., PHP scripts) that performs the functions of sending requests toexternal system for order cancellation, emailing, updating databaseentries, and/or synchronizing prescription data between differentservers.

The processing server 102 may, during execution of an instance of anexemplary routine, be configured to detect the absence of data needed tocomplete the execution of the instance of the exemplary routine. Thedata needed to complete the execution of the instance of the exemplaryroutine may be, for example, a prescription authorization for a productwhich a customer has placed an order for. The processing server 102 may,in response to the absence of the data needed, be configured toautomatically transmit a request for the data to an entity. The entitymay be an authorizing entity. For example, the processing server 102 maytransmit an authorization form for a prescription medicine to aveterinarian, a clinic, or some other authorizing entity. The entity mayreceive the request for data (e.g., a prescription authorization form)and enter the requested data. The entity may transmit back to theprocessing server the requested data, where the data is in an electronicformat and/or where the data was handwritten. For example, theauthorizing entity may receive a prescription authorization form thatthe entity may then fill out with handwritten information, informationtyped into the form via a customer device 116, or a combination of both.The prescription authorization form containing the requested data may bescanned into an electronic format which is then sent to processingserver 102 or it may be sent via fax, or mail.

The processing server 102 may be configured to automatically populatedata corresponding to the data received from the entity. The processingserver 102 may be configured to store the data received from the entityin a database (e.g., database 110). In some instances, the processingserver 102 may receive documentation including information to be storedin a database (e.g., database 110) that requires additional processingbefore the information can be stored in said database. For example, afax of the prescription authorization form is sent from a veterinarian,or veterinarian clinic, and received by processing server 102. For thisreason, the processing server 102 may be configured to communicate withan optical character recognition (OCR) server 112. The OCR server 112may be configured to receive one or more documents from processingserver 102 for which optical character recognition is required. Forexample, processing server 102 transmits the prescription authorizationform, or a copy thereof, to OCR server 112. The OCR server 112 may beconfigured to receive the documentation (e.g., the prescriptionauthorization) and perform optical character recognition to create adatafile containing optical character recognition data associated withthe documentation. The OCR server 112 may transmit the created datafileto processing server 102. The processing server 102 may be configured toautomatically store the datafile received from OCR server 112 in adatabase (e.g., database 110). The processing server 102 may beconfigured to apply regular expression matching logic to the datafilereceived from OCR server 112 to identify data associated with at leastone of: owner name, pet name, record identifier for a prescription,clinic name, authorization status, refill authorization data, and reasonfor requiring compound prescriptions, or any combination thereof.

A user (e.g., administrator 118, developer 120) may desire to create anexemplary routine in response to a business process for which system 100has no automated process in place to accomplish. The business processmay be related to a customer service need such as the editing orcancelling of an order. Referring to FIG. 3 , there is illustrated anexemplary flow chart for a method of creating an exemplarypre-programmed routine in accordance with an embodiment of the presentdisclosure. The method 300 may include the step 302 of creating one ormore new pre-programmed element types and/or a new instance of anexemplary routine. A pre-programmed element type may refer to a namegiven to a pre-programmed element (e.g., rxmTransmission,cancelpetscriptionrelease). The method 300 may include the step 304 ofcreating a new exemplary routine for each pre-programmed elementincluded in the instance of the exemplary routine. The new exemplaryroutine may define the sequence of execution for the pre-programmedelements included in the instance of the exemplary routine. The method300 may include the step 306 of creating computer executable code foreach pre-programmed element type created in step 302. The creation ofcomputer executable code may be accomplished by a developer 120.

The method 300 may include the step 308 of creating computer executablecode or a custom process module (CPM) that is configured to triggercreation of the instance of the exemplary routine. The method 300 mayinclude the step 310 of implementing business rules to call the code orCPM created in step 308 when pre-defined criteria are met. For example,at step 310 an administrator may define events that trigger the creationof an instance of an exemplary routine for execution of the instance ofthe exemplary routine to complete the relevant task (e.g., processing areturn to inventory after a product order has been canceled).

Referring to FIG. 4 , there is illustrated an exemplary flow chart for amethod of creating an instance of an exemplary routine in accordancewith an embodiment of the present disclosure. The method 400 may includethe step 402 of initiating a new instance of an exemplary routine. Theinitiation of a new instance of an exemplary routine may be caused by anexisting business process CPM and/or a trigger within existing codeoperating within one or more servers of system 100 (e.g., a trigger setwithin a pre-programmed element running in an instance of an exemplaryroutine). Initiating an instance of an exemplary routine may includestarting execution of code that creates a new instance of the exemplaryroutine. The step 402 may be initiated automatically (e.g., by atrigger) or by a user (e.g., an administrator 118, a developer 120). Forexample, a disposition on an incident being updated in database 110and/or an inbound email having a specific subject being added todatabase 110.

The method 400 may include the step 404 of automatically identifying thepre-programmed elements that are included in the instance of theexemplary routine initiated in step 402. A processing LU operating inconnection with processing server 102 may be configured to perform step404. For example, the molecule_utility function of the processing LU mayidentify the pre-programmed elements included in the instance of theexemplary routine. The method 400 may include the step 406 ofdetermining whether the pre-programmed elements identified in step 404should be cancelled. For example, in step 406 it may be determinedwhether the type of pre-programmed element and/or instance of theexemplary routine allows duplicates. An example of a pre-programmedelement that allows duplicates may be an element that is configured towrite a log file. An example of an instance of an exemplary routine thatdoes not allow duplicates may be an instance of an exemplary routinethat sends an electronic message to a customer. If the pre-programmedelements should be cancelled, the method 400 may progress to step 408 inwhich existing instances of pre-programmed elements not in a locked orcomplete state, that are included in the instance of the exemplaryroutine, are set to a cancelled state. If the pre-programmed elementsshould not be cancelled, the method 400 may progress to step 410 inwhich an instance of each required pre-programmed element, as defined bythe instance of the exemplary routine, is created in database 110. Theprocessing server 102 may be configured to perform steps 406-410 ofmethod 400.

Referring to FIG. 5 , there is illustrated an exemplary flow chart for amethod of executing instances of pre-programmed elements in accordancewith an embodiment of the present disclosure. The method 500 may includethe step 502 of requesting pending pre-programmed elements at apredetermined interval (in FIG. 5 the predetermined interval is oneminute). The pre-determined interval may be 30 seconds, 60 seconds, 90seconds, 120 seconds, 150 seconds, or 180 seconds. The monitoring server104 may be configured to perform step 502 (e.g., by access a monitoringLU). The method 500 may include the step 504 of identifying the nextpre-programmed element for each instance of a pending exemplary routine.The processing server 102 may be configured to perform step 504. Themethod 500 may include the step 506 of submitting the pre-programmedelements identified in step 504 for parallel processing. The step 506may further include returning the pre-programmed elements identified instep 504 to the monitoring server 104. For example, a list of IDs of theinstances of pre-programmed elements that are pending are sent tomonitoring server 104. In some embodiments, the IDs included in the listare specific to each instance of the pre-programmed elements. Forexample, there may be two unique IDs identifying different instances ofthe same pre-programmed element. The processing server 102 may beconfigured to perform step 506.

The method 500 may include the step 508 of initiating the parallelrequests to process the pre-programmed elements. The method 500 mayinclude the step 510 of determining whether there are pre-programmedelements to be processed. If there are pre-programmed elements to beprocessed, the method proceeds to step 512 in which the next IDcorresponding to a pre-programmed element is selected. In step 512, thesystem 100 may be configured to divide the total number of pendinginstances of pre-programmed elements by the number of parallel requests,each request being assigned a set of IDs corresponding to instances ofpre-programmed elements to iterate through. For example, pendinginstances of a pre-programmed element may be parsed into groups forparallel processing. The number of pending instances of pre-programmedelements that can be included in a single group of instances forparallel processing may be a configurable amount (e.g., 10, 20, 50, or100 instances for each group for parallel processing). If there are nopre-programmed elements to be processed, execution may be terminated.

The method 500 may also proceed to step 514 following step 512 todetermine if there is sufficient time to process an instance of thepending pre-programmed element. For example, the monitoring server 104may determine, based on the frequency established in step 502 (e.g., oneminute), if there is sufficient time remaining to process an instance ofthe pending pre-programmed element. The method 500 may include the step516 of transmitting the pre-programmed element ID and the remaining timedetermined in step 514 to the worker server 106. The monitoring server104 may be configured to perform steps 508 through 516. The method 500may include the step 518 of identifying the pre-programmed element typeand executing the code associated with the pre-programmed element type.The worker server 106 may be configured to perform step 518. The method500 may include the step 520 of determining whether an executingpre-programmed element is defined as “long-running”. A long-runningpre-programmed element may be a pre-programmed element that takes anamount of time to finish execution that is greater than a predefinedtimeout value. For example, a predetermined timeout value may be fiveminutes and pre-programmed element A may take ten minutes to execute,resulting in pre-programmed element A being defined as long-running.

If the pre-programmed element is defined as long running, the method mayproceed to step 522 to set the pre-programmed element as having a lockedstate. A locked state of an instance of a pre-programmed element mayallow execution of that instance of the pre-programmed element tocontinue across multiple execution runs without execution of saidinstance being restarted. A single execution run may refer to theexecution of instances of pre-programmed elements executing within thepredetermined interval (e.g., one minute) defined in step 502. If thepre-programmed element is not defined as long-running, the method 500may proceed to step 524 to determine the outcome of the executedpre-programmed element. If the pre-programmed element successfullyexecuted, the method 500 may proceed to step 526 to mark thepre-programmed element as complete. If the pre-programmed element failsto execute or runs out of time, the method 500 may proceed to step 528to increase the retry count associated with the instance of thatpre-programmed element. The method 500 may include the step 530 oftransmitting the status of an instance of the pre-programmed element tomonitoring server 104. The method 500 may return to step 512, followingthe transmission of the status in step 530, such that the next IDcorresponding to a pre-programmed element is selected and steps 514-530are repeated for each pre-programmed element to be processed. Theprocessing server 102 may be configured to perform steps 520 through530.

Referring to FIGS. 6A-6H, there is shown an exemplary user interface forthe creation of a new exemplary routine and/or pre-programmed elementsin accordance with an embodiment of the present invention. The exemplaryuser interfaces shown in FIGS. 6A-6H may be displayed on a client device108 in communication with processing server 102. Processing server 102may transmit the user-interfaces shown in FIGS. 6A-6H for display onclient device 108 via a network (e.g., wireless network, ethernetnetwork). The user interfaces illustrated in FIGS. 6A-6B and 6D-6H maybe a portion of an administrator UI, as described above with referenceto FIG. 1 . Referring to FIG. 6A, an administrator 118, via clientdevice 108, may define a new instance of an exemplary routine (e.g., mayinput a label for the new instance of the exemplary routine). Referringto FIG. 6B, the administrator 118, via client device, may provide inputto create a new pre-programmed element type to be included in theinstance of the exemplary routine shown in FIG. 6A. In this example, theadministrator 118 creates a new pre-programmed element labeled“cancelpetscriptionreleasesendemail”.

The administrator 118 may input a label that is representative of thetask that the pre-programmed element is configured to accomplish. Inthis example the pre-programmed element is configured to notify acustomer via an electronic message (e.g., email) that their prescriptionhas been cancelled, which may occur after the prescription cancellationis successful. In one embodiment, the successful execution of aninstance of an exemplary routine may be the trigger event for creationof a new instance of an exemplary routine. For example, an instance ofexemplary routine A successfully executes which triggers creations of aninstance of exemplary routine B to be executed. Referring to FIG. 6C,the administrator 118, following the creation of the new pre-programmedelement in FIG. 6B may coordinate with a developer 120 to develop thecomputer executable code for accomplishing the desired task. FIG. 6Cdisplays an example of computer executable code, written by a developer120, to accomplish the task of the pre-programmed element created inFIG. 6B. The computer executable code, written by the developer 120, maybe self-contained and may be used across a plurality of differentexemplary routines.

Referring to FIG. 6D, the administrator 118, via client device 108 maydefine an exemplary routine. The displayed administrator UI shown heremay be configured to allow the administrator to input the exemplaryroutine, select a specific pre-programmed element included in theexemplary routine, and define the sequence number associated with saidpre-programmed element. In the example shown here, the pre-programmedelement “cancelpetscriptionrelease” is assigned a sequence number of “1”indicating that “cancelpetscriptionrelease” is to be the firstpre-programmed element executed in this exemplary routine. Referring toFIG. 6E, the administrator 118, via client device 108, may add anotherpre-programmed element to the exemplary routine created in FIG. 6D. Inthis example, the administrator 118, adds the pre-programmed element“cancelpetscriptionreleasesendemail” to the exemplary routine andassigns a sequence number of “2” indicating that“cancelpetscriptionreleasesendemail” is to be the second pre-programmedelement executed in this exemplary routine.

Referring to FIGS. 6F-6H, there is illustrated an exemplary userinterface for creating and executing a new instance of an exemplaryroutine. Referring to FIG. 6F, an incident may trigger creation of aninstance of an exemplary routine. In this example, the instance createdis for the exemplary routine created by the administrator 118 in FIG.6A.

The incident that triggers creation of the instance of an exemplaryroutine may be any one of: administrative workflow, custom code, or anew instance of a pre-programmed element (of a specific type) beingcreated. Referring to FIG. 6G, upon creation of a new instance of anexemplary routine, the processing server 102 is configured to createinstances of the pre-programmed elements included in the exemplaryroutine. The instances of the pre-programmed elements may be stored indatabase 110. In the example shown here, an instance report for theinstances of pre-programmed elements is displayed. The displayedinstance report may include information associated with each instance ofpre-programmed elements including: an ID, the label, a state (e.g., thestatus), a retry count, associated data, contact data, an incident ID,an organization number, and the date last updated. Referring to FIG. 6H,the computer executable code for each instance of the pre-programmedelements is executed in sequence. A display of a completed instance of apre-programmed element is displayed in FIG. 6H.

Referring to FIG. 6I there is shown a customer service user interfacedisplayed on a client device 108 in accordance with an exemplaryembodiment of the present invention. The processing server 102 may beconfigured to transmit the customer service user interface for displayon the client device 108. The customer service user interface mayinclude information specific to a customer and/or an order placed, viastorefront server 107, by said customer. In the customer service UIexample displayed in FIG. 6I, information relating to the customer andan order placed by the customer is shown. The customer service UI maydisplay user-operable buttons configured to allow an admin 118 to takeactions related to the displayed order and/or customer. For example, thecustomer service UImay display buttons that allow an admin 118 torequest a return of the ordered product, email the customer, associate apet with the customer, and/or edit customer contact information. Theprocessing server 102 may be configured to, in response to an input froman admin 118 on the customer service UI, trigger creation of an instanceof an exemplary routine corresponding to the input from the admin 118.For example, an admin 118 may input on customer service UI to request areturn for a product ordered by the customer. In response to the inputfrom admin 118, the processing server 102 may execute code to create aninstance of an exemplary routine configured to process a request toreturn said product and store said instance of the exemplary routine indatabase 110 for execution.

Referring to FIG. 7 , there is illustrated an exemplary flowchart for amethod of execution of an instance of an exemplary routine. The method700 shown in FIG. 7 represents an exemplary method implemented by system100 without any interruptions (e.g., failure to execute pre-programmedelements, changes in underlying data). The method 700 may start at step702 in response to a trigger event (e.g., an incident). The triggerevent may be an organization object being toggled to “digital”. Anorganization object being toggled to “digital” may refer to anindication in database 110 that a veterinary clinic should use aprescription authorization service offered by a host of the processingserver 102 (e.g., Petscriptions by Chewy) or a fax to authorizeprescriptions. The method 700 may include step 704 where an instance ofan exemplary routine is created. The method 700 may include the step 706where instances of pre-programmed elements included in the instance ofthe exemplary routine are created. The method 700 may include the step708 where processing is delayed until Cron executes, which may refer toa time-based scheduler that defines a configurable set of time betweenexecution of different instances of pre-programmed elements. The method700 may include the step 710 where an instance of a pre-programmedelement that is listed as the first pre-programmed element in a sequencedefined by the instance of the exemplary routine is executed. The method700 may include the step 712 where processing is delayed. The method 700may include the step 714 where one or more instances of pre-programmedelements are executed in parallel. In some embodiments, step 710 mayalso include parallel execution of instances of pre-programmed elements.In some embodiments, step 714 executes only one instance of apre-programmed element. The instances of pre-programmed elementsexecuted in step 714 may correspond to the next sequence ofpre-programmed elements as defined by one or more instances of exemplaryroutines. The method 700 may include step 716 where processing isdelayed. The method 700 may include step 718 where an instance of apre-programmed element next in the sequence is executed. It will beunderstood that the method 700 is an example, and that in practice anynumber of instances of pre-programmed elements may be executed accordingto a corresponding sequence defined by an instance of an exemplaryroutine.

In some embodiments, instances of exemplary routines that havesuccessfully executed and/or failed to execute are stored as records indatabase 110 for auditing purposes. An instance of an exemplary routine,once it has successfully executed or failed to successfully execute, mayhave the status indicator updated respectively. For example, an instanceof an exemplary routine may include a “success” indicator for eachinstance of pre-programmed elements included in the instance of theexemplary routine that successfully executed and a “failed” statusindicator for instances of pre-programmed elements that failed toexecute.

Referring to FIG. 8 , there is illustrated an exemplary flowchart for amethod of execution of an instance of an exemplary routine where apre-programmed element fails to execute. The method 800 may be similarto the method 700, shown in FIG. 7 , except that an instance of apre-programmed element fails to execute. Specifically, the steps 802 to814 of method 800 correspond to the steps 702 to 714 of method 700 andwill not be repeated for sake of brevity. In the method 800, executionof the second sequence of an instance of a pre-programmed element fails.Following the instance of the pre-programmed element failing to execute,the method 800 includes the step 816 of setting the pre-programmedelement to a failed status. The method 800 may include a delay inprocessing at step 818. The method 800 may include the step 820 ofattempting execution of the previously failed pre-programmed element onemore time. In the method 800, the attempt at executing the instance ofthe pre-programmed element in step 820 is successful and the instance ofthe pre-programmed element executes. Following the successful executionof the instance of the pre-programmed element, method 800 proceeds tosteps 822 to 824, which correspond to steps 716 and 718 of method 700and will not be described again for sake of brevity.

Referring to FIG. 9 , there is illustrated an exemplary flowchart for amethod of execution of an instance of an exemplary routine where apre-programmed element permanently fails to execute. The method 900 issimilar to the method 800 except that the instance of the pre-programmedelement that fails to execute does not successfully execute after acertain number of attempts. Specifically, the steps 802 to 818 of method800 correspond to the steps 902 to 918 of method 900 and will not berepeated for sake of brevity. In this example, after the first reattemptfails, the method 900 returns to step 916 and increments a retry countassociated with the instance of the pre-programmed element by 1. Themethod 900 then attempts, a certain number of times, to successfullyexecute the instance of the pre-programmed element. In this example, thetotal number of attempted retries is five (a first reattempt followed byfour more). The instance of the pre-programmed element fails to executein each attempt and a retry threshold is reached. The retry thresholdmay be a predetermined amount established by a user (e.g., administrator118, developer 120).

Following the reattempts to execute the instance of the pre-programmedelement, the method 900 may include step 922 in which the instance ofthe pre-programmed element is marked as failed. The step 922 may alsoinclude adding the instance of the pre-programmed element to a list ofinstances of pre-programmed elements that failed to execute after acertain number of retries. The method 900 may include the step 924 ofautomatically generating and sending a report that notifiesadministrators 118 and/or developers 120 of all instances ofpre-programmed elements that failed to execute after a certain number ofretries. The system 100 may be configured to automatically perform step924 at a predetermined interval (e.g., every 6 hours, every 12 hours,every 24 hours, every 3 days, every week). The method 900 may includethe step 926 of resolving the error causing the failure of the instanceof the pre-programmed element. For example, the error may be caused by anetwork cable not being plugged in, which requires an administrator tomanually connect a network cable. In other embodiments the system 100may be configured to automatically resolve the error. The method 900 mayinclude the step 928 of manually resetting the retry count for theinstances of the failed pre-programmed elements. Step 928 may beperformed after the error has been resolved. In some embodiments,resetting the retry count for the failed instances of pre-programmedelements may cause execution to be reattempted for said instances. Themethod 900 may include the step 930 of setting the instance of thefailed pre-programmed element to complete. Step 930 may be performedafter an admin 118 or developer 120 has manually fixed the error whichcaused the instance of the pre-programed element from step 920 to fail.Following step 930, method 900 proceeds to steps 932 to 934 whichcorrespond to steps 822 and 824 of method 800 and will not be describedagain for sake of brevity.

Referring to FIG. 10 , there is illustrated an exemplary flowchart for amethod of execution of an exemplary routine with a long-runningpre-programmed element. The method 1000 may be similar to the method 700shown in FIG. 7 , except that there is an instance of a long-runningpre-programmed element to be executed. Specifically, the steps 1002 to1014 of method 1000 correspond to the steps 702 to 714 of method 700 andwill not be repeated for sake of brevity. In the method 1000, there isan instance of a long-running pre-programmed element that beginsexecuting at step 1014. The method 1000 includes the step 1016 ofmarking the instance of the long-running pre-programmed element as“long-running” and setting it to a “locked” status. The method 1000includes the step 1018 of delaying processing. The method 1000 includesthe step of determining whether the instance of the long-runningpre-programmed element is complete. If the instance long-runningpre-programmed element has not finished executing, the method 1000repeats step 1018 (e.g., continues to delay processing). If the instanceof the long-running pre-programmed element has finished executing, themethod 1000 continues to steps 1022 and 1024 which correspond to steps716 and 718 of method 700 and will not be described again for sake ofbrevity.

Referring to FIG. 11 , there is illustrated an exemplary flowchart for amethod of execution of an instance of an exemplary routine where theexemplary routine is updated mid-execution. The method 1100 may besimilar to the method 700 shown in FIG. 7 , except that there is theexemplary routine is redefined while an instance of the exemplaryroutine is being executed. Specifically, the steps 1102 to 1112correspond to the steps 702 to 712 of method 700 and will not berepeated for the sake of brevity. In the method 1100, following thedelay in processing at step 1112, an administrator 118, at step 1114,redefines the exemplary routine that the instance currently beingexecuted corresponds to. In this example, an administrator 118 removes apre-programmed element from the exemplary routine. It will be understoodthat a modification to the exemplary routine may include anymodification that would cause an instance of an exemplary routine,created subsequent to the instance currently executing and themodification being performed, to execute differently than a previouslyexecuted and/or currently executing instance of said exemplary routine.For example, a modification may include a modification to the sequencedefined by the exemplary routine, the addition of a pre-programmedelement to the exemplary routine, and/or the removal of a pre-programmedelement from the exemplary routine.

The method 1100 proceeds, at step 1116, to execute the instances ofpre-programmed elements that were included in the instance of theexemplary routine prior to the administrator 118 removing thepre-programmed element at step 1114. Following step 1114, the method1100 proceeds to steps 1116 through 1120 that correspond to steps 714 to718 of method 700 and will not be described again for sake of brevity.In this example, the grouping was redefined while an instance of it wasexecuting, and therefore the instance may be executed based on thegrouping prior to the change made by the administrator 118 at step 1114.However, future instances of the same grouping may execute according tothe change made by the administrator 118 in step 1114. It will beunderstood that the redefining of the exemplary routine instances mayhappen at any point after step 1104 and prior to termination of theinstance of the pre-programmed element without affecting the outcome ofthe instance of the pre-programmed element.

In some embodiments, some instances of exemplary routines are the same(e.g., contain the same or substantially the same code and point to thesame data or types of data). In some embodiments, some of the pluralityof instances of exemplary routines differ from one another (e.g., thecode may have been changed or the data may have changed in anintervening time period between the creation of instances of exemplaryroutines). For example, the code associated with a particularpre-programmed element be may be changed after a first instance of anexemplary routine is created. That first instance would persist in thatthe original pre-programmed element code would remain unchanged, butfuture instances of such exemplary routine would reflect the new code.For example, in some instances there may be instances of exemplaryroutine X stored in database 110 and instances of different exemplaryroutines Y stored in database 110. For example, a first instance ofexemplary routine X may be configured to cancel an order for customer A(e.g., the first instance was created in response to an incident tocancel an order from customer A) and a second instance of exemplaryroutine X may be configured to cancel an order for customer B (e.g., thesecond instance was created in response to an incident to cancel anorder from customer B). Both the first and second instance of exemplaryroutine X may be stored in database 110. At a later point in time theremay be a modification to exemplary routine X, and subsequent to thatpoint in time there may be an instance of exemplary routine X created tocancel an order for customer C. In one embodiment, the configuration ofthe instances of the exemplary routine for customer A and customer Bwould be the same and would differ from the instance of the exemplaryroutine for customer C.

Referring to FIG. 12 , there is illustrated an exemplary flowchart for amethod of execution of an instance of an exemplary routine whereunderlying records are modified mid-execution. The method 1200 may besimilar to the method 700 shown in FIG. 7 , except that underlyingrecords required for the instances of the pre-programmed elements toexecute are modified mid-execution. Specifically, the steps 1202 to 1212correspond to steps 702 to 712 of method 700. Following the delay inprocessing 1212, an administrator modifies a record required by one ormore of the instances of pre-programmed elements created in step 1206.The method 1200 continues to step 1216 to cancel the instance of theexemplary routine. The method continues to step 1218 to create a newinstance of the exemplary routine which may correspond to the sameexemplary routine for which the instance cancelled in step 1216 wasoriginally created. To put it another way, in steps 1216 and 1218, thecurrently executing instance of the exemplary routine is cancelled andrestarted. Following the restart at step 1218, the method 1200 continuesto steps 1220 through 1230, which correspond to steps 706 to 718 ofmethod 700 and will not be described again for sake of brevity.

Referring to FIG. 13 , there is illustrated an exemplary flowchart for amethod of execution of an instance of an exemplary routine whereunderlying records are modified mid-execution. The method 1300 may besimilar to the method 1200, except that the instance of the exemplaryroutine that is currently executing is not cancelled and restarted.Steps 1302 to 1314 correspond to steps 1202 to 1214 of method 1200.However, in method 1300, following the modification of records, theinstance of the exemplary routine created at step 1304 continues toexecute through steps 1316 to 1322. Put another way, regardless of themodification of the underlying records, the currently executing instanceis not cancelled and restarted. Steps 1316 to 1322 correspond to steps712 to 718 of method 700 shown in FIG. 7 , and will not be describedagain for sake of brevity.

Referring to FIG. 14 , there is shown a flow diagram of an exemplarymethod 1400 for performing a fault tolerant automated sequence ofcomputer implemented tasks. In an embodiment, the method 1400 includes astep 1402 of presenting, for selection by a user (e.g., administrator118), a plurality of pre-programmed elements, each pre-programmedelement being independently executable relative each otherpre-programmed element such that an output of any of the pre-programmedelements is not a direct input to any other of the pre-programmedelements. For example, an administrator 118 via a client device 108 incommunication with processing server 102 displays the admin UI to allowthe administrator to create an instance of an exemplary routine as shownin FIGS. 6A-6B. In an embodiment, method 1400 also includes the step1404 of receiving from the user a selection of one or more of thepre-programmed elements and a sequence for performing eachpre-programmed elements in the selection to form an exemplary routine.For example, an administrator 118, via client device 108, creates anexemplary routine as shown in FIGS. 6E-6F.

In some embodiments, the method 1400 also includes the step 1406 ofcreating an instance of the exemplary routine in response to a requestto implement the exemplary routine. A request to implement an exemplaryroutine may be a request to perform a series of tasks in response to anincident, as described above. In some embodiments, the instance of theexemplary routine includes an instance of each of the selectedpre-programmed elements arranged for performance in accordance with thesequence and is configured to perform tasks defined by thepre-programmed elements and the sequence. For example, at steps 702 to706 of method 700, an instance of an exemplary routine is created inresponse to a trigger event and instances of each pre-programmed elementincluded in the exemplary routine are created. In an embodiment, themethod 1400 also includes the step 1408 of initiating implementation ofthe instance of the exemplary routine by initiating performance of theinstances of the pre-programmed elements in accordance with thesequence. For example, at steps 710 to 718 of method 700, the instancesof the three pre-programmed elements included in the exemplary routineare executed in sequence. In an embodiment, the method 1400 alsoincludes the step 1410 of detecting an error that prevents thecompletion of at least one instance of the pre-programmed elements. Forexample, in step 816 of method 800, an instance of the secondpre-programmed element in the sequence defined by an instance of anexemplary routine is detected. In an embodiment, the method 1400 alsoincludes the step 1412 of terminating the implementation of the instanceof the exemplary routine upon detection of the error without userintervention. For example, in steps 916 to 922 of method 900 an instanceof a pre-programmed element fails after a certain number of retries andthe instance of the exemplary routine is automatically terminated.

In some embodiments, the independently executable pre-programmedelements of method 1400 may not require data generated from anotherpre-programmed element in order to complete execution. In someembodiments, each independently executable pre-programmed elementcompletes using data from a data field, where the data is at least oneof: i) populated in the data field before the creating of the instanceof the exemplary routine; and ii) updated after the initiating of theimplementation of the instance. For example, each instance of apre-programmed element may use data stored in database 110 that wasstored prior to the creation of the instance of the pre-programmedelement or data that was updated in database 110 after the instance ofthe pre-programmed element was created.

In some embodiments, the method 1400 may include transmitting anotification that at least one instance of a pre-programmed element didnot execute to completion and the notification includes at least one of:i) all instance of exemplary routines that are in a failed state at thetime the notification is transmitted; ii) the instances of apre-programmed elements associated with each instance of exemplaryroutines that are in the failed state; iii) the instance of theexemplary routine; iv) a number of retries associated with each instanceof the exemplary routine in the failed state; and v) a database objectassociated with each instance of the exemplary routine in the failedstate. For example, in step 924 of method 900 a report is sent toadministrators 118 including a listing of all instances ofpre-programmed elements that failed to execute. Administrators 118 maythen review and/or analyze the instance of the pre-programmed elementand/or the associated exemplary routine on the system 100 to identifyerror(s) that caused the instance to fail.

In some embodiments, the method 1400 includes updating one or more ofthe pre-programmed elements of the exemplary routine after theinitiating implementation step and creating a subsequent instance of theexemplary routine in response to a subsequent request to implement theexemplary routine after the updating step, the subsequent instance ofthe exemplary routine including an instance of the one or more updatedpre-programmed elements of the exemplary routine. For example, in themethod 1100 shown in FIG. 11 , an administrator 118 updates an exemplaryroutine corresponding to a currently executing instance of saidexemplary routine. The instance of said grouping completes executionbased on the grouping prior to the update and subsequent instances ofsaid grouping would execute based on the update from the administratorat step 1114.

In some embodiments, the method 1400 may include simultaneouslyimplementing a plurality of instances of the same exemplary routine. Forexample, the system 100 is configured to execute, in parallel, aplurality of instances of the same exemplary routine (e.g., fourinstances of exemplary routine A being executed in parallel). In someembodiments, the method 1400 may include simultaneously implementing atleast one instance of the exemplary routine and at least one instance ofthe subsequent exemplary routine. For example, the system 100 may beconfigured to execute an instance of an exemplary routine according tomethod 1100 and simultaneously execute an instance of the updatedexemplary routine based on the updates made at step 1114.

In some embodiments, at least some of the instances of the exemplaryroutine are initiated at a different time than other instances of thesame exemplary routine that are being simultaneously implemented. Forexample, three instances of exemplary routine A may be executed inparallel at a first time, and at a second time different than the firsttime, a fourth instance of exemplary routine A may be executed. In someembodiments, updating the one or more of the pre-programmed elementsincludes receiving and storing revised code for performing a task. Forexample, in step 1114 of method 1100 the updates made to the exemplaryroutine may include an update to the executable code of a pre-programmedelement included in the grouping.

In some embodiments, the method 1400 may include, after the detectingstep and before the terminating step, attempting to re-implement atleast one instance of the pre-programmed elements associated with thedetected error. For example, in steps 816-820 of method 800 an instanceof a pre-programmed element, which failed to execute, is retried. Insome embodiments an error is detected based upon a pre-defined numberattempts to execute an instance of a pre-programmed element. In oneembodiment, the pre-defined number of attempts is stored in an attemptsfield in the database. In some embodiments, each attempt to executecorresponds to an incremented value of a retry count in a retry field(e.g., up to the pre-defined number of retry attempts is performed). Insome embodiments, the method 1400 may include detecting a trigger eventthat triggers, without user intervention, a re-initiation of theperformance of the instance of at least one of the pre-programmedelements and wherein an error state that prevents the completion of theat least one instance arises after a subsequent trigger event isdetected following a pre-selected number of re-initiations of theperformance of the at least one instance of the pre-programmed element.

In some embodiments, the method 1400 may include the steps of defining aretry threshold value for each of the pre-programmed elements, and afterthe detecting step and before the terminating step, attempting tore-implement the at least one instance of the pre-programmed elementsassociated with the detected error in accordance with the retrythreshold value. For example, in the method 900 shown in FIG. 9 , thesystem 100 is configured to retry an instance of a failed pre-programmedelement in steps 916-920 five times.

In some embodiments, the method 1400 may include the steps of duringimplementation of the instance of the exemplary routine, detecting theabsence of prescription authorization data needed to complete theimplementation of the instance of the exemplary routine, based on theabsence of the prescription authorization, automatically transmitting anauthorization form to an authorizing entity, receiving an authorizationfacsimile of a completed form in response to the automatic transmittingand automatically populating a prescription authorization field basedupon the received facsimile. For example, during execution of aninstance of an exemplary routine, the system 100 may be configured todetermine that there is no record of a prescription authorizationrequired for an instance of a pre-programmed element to perform itsintended task. In response, the system 100 may transmit a prescriptionauthorization form to an authorizing entity (e.g., a veterinarian) whothen receives and inputs the information required by the prescriptionauthorization form. The authorizing entity may transmit the completedprescription authorization form in the form of a facsimile. The system100 may be configured to receive the facsimile and automaticallyupdate/populate records in database 110 based on the information in thereceived facsimile.

In some embodiments, the method 1400 includes receiving a datafilecontaining optical character recognition data associated with theauthorization facsimile. For example, the system 100 may be configuredto perform optical character recognition on the received facsimile inorder to convert the information on the received facsimile to computerreadable text which can then be updated/populated in database 110. Insome embodiments, the method 1400 may include automatically storing thedatafile containing optical character recognition data in a securedatabase based upon the automatically populating the prescriptionauthorization field. In some embodiments, regular expression matchinglogic is applied to the datafile containing optical characterrecognition data to identify data associated with at least one of: ownername, pet name, record identifier for a prescription, clinic name,authorization status, refill authorization data, reason for requiringcompound prescription and combinations thereof. In some embodiments, thesimultaneously implemented plurality of instances of the exemplaryroutines are complex operations related to prescription authorizationimplementations as described herein (e.g., by automatically processingfax prescriptions). In some embodiments, at least 100 complex routinesare performed simultaneously per minute.

In some embodiments, the method 1400 further includes the steps ofadding or removing at least one selected pre-programmed element from theexemplary routine after the initiating implementation step, and creatinga subsequent instance of the exemplary routine in response to a subsequent request to implement the exemplary routine after the adding orremoving step, the sub sequent instance of the exemplary routinereflecting the addition or removal of the at least one selectedpre-programmed element in accordance with the adding or removing step.For example, in step 1114 of method 1100, the administrator 118 mayupdate the exemplary routine having a corresponding instance which iscurrently executing to remove a pre-programmed element. The instance,which is currently executing, executes based on the grouping and/orexemplary routine prior to the update at step 1114. However, subsequentinstances may execute based on the update and would therefore notinclude an instance of the pre-programmed element which was removed instep 1114 (e.g., the method 700 of FIG. 7 terminating after step 714).

In some embodiments, one or more data objects are not populated at thetime of creating of an instance of the exemplary routine but arepopulated later in order for the instance of the exemplary routine tocomplete. For example, when selecting a new pre-programmed element anadministrator would preferably identify the data that are required forthe particular prep-programmed element (e.g., incident data, contactdata, organization data shown in FIG. 2 ). Alternatively, the particulardata required by the pre-programmed element may be automaticallyidentified through the execution of separate pre-programmed elements. Inone embodiment, when an instance of a pre-programmed element is createdat runtime, the system verifies that a record associated with therequired data is associated with the request (e.g., the creation of theinstance). For example, the system 100 may be configured to use specificdata such that the system 100 may verify that a record associated withthe specific data is associated with the creation of the instance of theexemplary routine. When an instance of a pre-programmed elementrequiring the said specific data is requested, the system 100 may beconfigured to verify that a record associated with the required dataelements, stored in database 110, is associated with the request for theinstance of the pre-programmed element. In some embodiments, loggingexists out-of-band. For example, the system 100 may be configured to, inthe event that an instance of a pre-programmed element fails to execute,detect the failure to execute, log the failure to execute, and transmitan indication that the instance of the pre-programmed element failed toexecute (e.g., steps 916-924 of method 900).

In some embodiments, the method 1400 includes the steps of receivingfrom a user, trigger instructions defining at least one triggercondition, and wherein the creating of an instance of the exemplaryroutine is based upon a recognition that at least one of the triggerconditions has been met. For example, an administrator 118 may, via theadmin UI, define incidents that trigger the creation of an instance ofan exemplary routine. In some embodiments, at least one triggercondition is a change in data state (e.g., change in underlying data).In some embodiments, each pre-programmed element operates on one or moreof: i) a defined data set; and ii) a variable data set (e.g., datapopulated in a particular data field may change over time). A defineddata set may be a row within a database table, stored in database 110,and the associated fields that a pre-programmed element requires forexecution. If one or more of the associated fields is null, or has avalue that is not expected by the pre-programmed element, the system 100may be configured to prevent a crash by retrying execution of theinstance of the pre-programmed element as described in method 900.

In some embodiments, the method 1400 includes the step of, upondetecting the error that prevents the completion of at least oneinstance of the pre-programmed elements, receiving an intervention tocomplete the at least one instance of the pre-programmed element. Forexample, in steps 926-930 of method 900 a user (e.g., admin 118 ordeveloper 120) resolves the error (e.g., step 926) and resets (e.g.,decrements in step 928) the retry count and performs execution of theexemplary routine. In some embodiments, resetting of the retry count isautomatically undertaken upon the execution of an intervention. Forexample, upon resolving the error the system 100 may be configured toautomatically reset the retry count. In some embodiments, the exemplaryroutine may include data object mapping that defines for each exemplaryroutine the location of data required by one or more pre-programmedelements within the exemplary routine. For example, each exemplaryroutine may include the ID, and or name of the pre-programmed elementsrequired for the exemplary routine. In some embodiments, the data objectmapping is based upon at least one of: i) mapping data received inresponse to a prompt presented to the user through a user interface; ii)a user selection based upon a predefined menu of mapping options; andiii) indicia associated with a trigger condition induces the creating ofan instance of the exemplary routine. For example, an email addressrequired by an instance of a pre-programmed element may be changed. Inresponse to that change, a new instance of the exemplary routine iscreated (e.g., steps 1214 to 1230 of method 1200). In some embodiments,the data object mapping is at least in part defined within thepre-programmed elements.

In some embodiments, the method 1400 includes the step of simultaneouslyimplementing one or more instances of an exemplary routine byimplementing instances of pre-programmed elements in parallel. Forexample, in step 714 of method 700 different instances of pre-programmedelements are being executed in parallel. Those instances ofpre-programed elements may be instances of the same pre-programmedelements included in instances of the same exemplary routine which isbeing executed by system 100 in parallel.

In some embodiments, the method 1400 includes the step of simultaneouslyimplementing one or more instances of an exemplary routine byimplementing instances of pre-programmed elements in series.

In some embodiments, the method 1400 includes the step of sequencing theperformance of pre-programmed elements by delaying instructions toimplement a pre-programmed element until at least one of anotherpre-programmed element achieves a predefined state. For example, theinstances of pre-programmed elements executed in step 824 do not happenuntil the instance of the pre-programmed elements in step 820 execute.In some embodiments, the predefined state includes at least one of: i) acompletion state; ii) a failure state. In some embodiments, thecompletion state includes at least a partial completion and the failurestate includes failure after a predetermined number of tries. In someembodiments, the completion state includes at least one of: i) complete;ii) partial complete; iii) failed to complete; iv) not started and v)delayed. The failed to complete state may refer to an instance of apre-programmed element that has failed, prior to a predetermined numberof tries occurring, to successfully execute. Put another way, in FIG. 9steps 916-920, an instance of a pre-programmed element may beretried/attempted up to five times and failed attempts to execute, up tothe five times, may result in a “failed to complete” status.

In some embodiments, at least one pre-programmed element is along-running pre-programmed element that is programmed to cause otherpre-programmed elements within an instance of the exemplary routine, inwhich an instance of the long-running element is included, to at leastone of: i) pause execution until the long-running element reaches acompletion state; and ii) delay completion until the long-runningelement reaches the completion state. For example, in steps 1016 to 1020in method 1000 the method 1000 does not progress past step 1020 untilthe instance of the pre-programmed element marked as having a lockedstatus in step 1016 is complete.

In some embodiments, the method 1400 includes the steps of: completingthe instance of the exemplary routine using the state of the respectiveinstances of pre-programmed elements after the instance of the exemplaryroutine has been created, wherein subsequent to the time the instance ofthe exemplary routine has been created, a change is made to theexemplary routine upon which the instance of the exemplary routine isbased, and interrupting the instance of the exemplary routine afterreceiving a call to interrupt the instance of the exemplary routinebased upon call to create a new instance of the exemplary routine usinga data site that also used by the instance of the exemplary routine andthe dataset includes a flag set to cause the interruption of theinstance of the exemplary routine.

In some embodiments, the method 1400 includes interrupting execution ofthe instance of the exemplary routine upon receipt of a triggeringevent. For example, the method 1200 at step 1216 cancels a pendinginstance of a pre-programmed element and restarts execution of theinstance of the corresponding exemplary routine in response to a changein underlying records at step 1214. In some embodiments, the method 1400includes interrupting execution of the instance of the exemplary routineupon receipt of a predetermined number of triggering events including atleast one of: i) a network timeout; ii) a system error. In someembodiments, the triggering event includes one or more of: i) a changeto a data record; or ii) a change to the pre-programmed element. In someembodiments, each pre-programmed element is fully executable withoutbeing directly dependent upon data generated by of any otherpre-programmed element. In some embodiments, the instance of theexemplary routine reaches a successful conclusion if all of thepre-programmed elements within the instance of the exemplary routine arecompleted.

It will be appreciated by those skilled in the art that changes could bemade to the exemplary embodiments shown and described above withoutdeparting from the broad inventive concepts thereof. It is understood,therefore, that this invention is not limited to the exemplaryembodiments shown and described, but it is intended to covermodifications within the spirit and scope of the present invention asdefined by the claims. For example, specific features of the exemplaryembodiments may or may not be part of the claimed invention and variousfeatures of the disclosed embodiments may be combined. Unlessspecifically set forth herein, the terms “a”, “an” and “the” are notlimited to one element but instead should be read as meaning “at leastone”.

It is to be understood that at least some of the figures anddescriptions of the invention have been simplified to focus on elementsthat are relevant for a clear understanding of the invention, whileeliminating, for purposes of clarity, other elements that those ofordinary skill in the art will appreciate may also comprise a portion ofthe invention. However, because such elements are well known in the art,and because they do not necessarily facilitate a better understanding ofthe invention, a description of such elements is not provided herein.

Further, to the extent that the methods of the present invention do notrely on the particular order of steps set forth herein, the particularorder of the steps should not be construed as limitation on the claims.Any claims directed to the methods of the present invention should notbe limited to the performance of their steps in the order written, andone skilled in the art can readily appreciate that the steps may bevaried and still remain within the spirit and scope of the presentinvention.

1-92. (canceled)
 93. A method for performing a fault tolerant automatedsequence of computer implemented tasks comprising: at a processingserver coupled to a database and a storefront server: rendering anadministrator facing UI at a client device coupled to the processingserver; presenting for selection by a user via the administrator facingUI a plurality of pre-programmed elements, each pre-programmed elementbeing independently executable relative each other pre-programmedelement such that an output of any of the pre-programmed elements is nota direct input to any other of the pre-programmed elements; receivingvia the administrator facing UI a selection of two or more of thepre-programmed elements and a sequence for performing eachpre-programmed elements in the selection to form an exemplary routinethat includes the two or more of the pre-programmed elements; receivingfrom the storefront server an indication of a first trigger eventcorresponding to an input at a customer facing UI, and in response toreceiving the indication of a trigger event, i) automatically creating afirst instance of the exemplary routine that includes an instance ofeach of the selected pre-programmed elements arranged for performance inaccordance with the sequence and being configured to perform tasksdefined by the pre-programmed elements and the sequence; and ii) settingto a pending execution status each instance of each of the selectedpre-programmed elements of the first instance of the exemplary routine;at a monitoring server coupled to the processing server and thedatabase, based on the execution status of each instance of the selectedpre-programmed elements of the first instance of the exemplary routine,transmitting a request to the processing server to initiate execution ofthe exemplary routine according to the sequence; and at the processingserver, automatically executing the instances of the pre-programmedelements according to the sequence in response to the request from themonitoring server.
 94. The method of claim 93 further comprising:detecting an error that prevents completion of at least one instance ofthe pre-programmed elements; and terminating the execution of the firstinstance of the exemplary routine upon detection of the error withoutuser intervention.
 95. The method of claim 94 further comprising: afterthe detecting step and before the terminating step, attempting tore-execute at least one instance of the pre-programmed elementsassociated with the detected error.
 96. The method of claim 94 furthercomprising: detecting a trigger event that triggers, without userintervention, a re-execution of the instance of at least one of thepre-programmed elements and wherein an error state that prevents thecompletion of the at least one instance arises after a subsequenttrigger event is detected following a pre-selected number ofre-executions of the at least one instance of the pre-programmedelement.
 97. The method of claim 94 further comprising: defining a retrythreshold value for each of the pre-programmed elements; and after thedetecting step and before the terminating step, attempting to re-executethe at least one instance of the pre-programmed elements associated withthe detected error in accordance with the retry threshold value.
 98. Themethod of claim 94 wherein the error that prevents completion includesan absence of prescription authorization data needed to complete theexecution; and based on the absence of the prescription authorization,automatically transmitting an authorization form to an authorizingentity; receiving an authorization facsimile of a completed form inresponse to the automatic transmitting; automatically populating aprescription authorization field based upon the received facsimile; andclearing the detected error to cause execution of the first instance ofthe exemplary routine to resume.
 99. The method of claim 93 furthercomprising: simultaneously executing one or more instances of instancesof pre-programmed elements in parallel.
 100. The method claim 93,wherein at least one pre-programmed element is a long-runningpre-programmed element that is programmed to cause other pre-programmedelements included in the first instance of the exemplary routine to atleast one of: i) pause execution until the long-running element reachesa completion state; ii) delay completion until the long-running elementreaches the completion state.
 101. The method of claim 93, wherein afailure to execute one instance of one of the pre-programmed elementsdoes not prevent the execution and completion of another instance of thesame pre-programmed element.
 102. The method of claim 93 furthercomprising: at the processing server, receiving from the storefrontserver, an indication of a second trigger event corresponding to asecond input at the customer facing UI, and in response to receiving theindication of the second trigger event, i) automatically creating asecond instance of the exemplary routine that includes an instance ofeach of the selected pre-programmed elements arranged for performance inaccordance with the sequence and being configured to perform tasksdefined by the pre-programmed elements and the sequence; and ii) settingto a pending execution status each instance of each of the selectedpre-programmed elements of the second instance of the exemplary routine;at the monitoring server, based on the execution status of each instanceof the second exemplary routine, transmitting a second request to theprocessing server to initiate execution of the second exemplary routineaccording to the sequence; and at the processing server, automaticallyexecuting the instances of the pre-programmed elements according to thesequence in response to the second request from the monitoring server.103. The method of claim 102, wherein the execution associated with thesecond request is independent of the execution associated with the firstrequest.
 104. The method of claim 102, wherein the second instance ofthe exemplary routine differs from the first instance of the exemplaryroutine based on an aspect of a pre-programmed element that was changedafter the first instance of exemplary routine was created.
 105. Themethod of claim 104, wherein the aspect of the pre-programmed elementthat changed includes at least one of: substitution of pre-programmedelements, addition of a pre-programmed element, alteration of apre-programmed element, elimination of a preprogrammed element, asequence change.
 106. A system for implementing a fault tolerantautomated sequence of computer implemented tasks comprising: astorefront server configured to cause a customer facing user interface(UI) display to render at one or more customer devices and to receiveone or more inputs via the customer facing UI; a database, coupled tothe storefront server and configured to store pre-programmed elementsthat each include an independently executable self-contained unit ofcomputer code configured to perform a specific task; a processing servercoupled to the database and the storefront server, the processing serverhaving a central processing unit, memory, an input port, and an outputport, the processing server being further coupled to a plurality ofclient devices, the processing server being configured to: render anadministrator facing UI at a client device coupled to the processingserver; present for selection by a user via the administrator facing UIa plurality of pre-programmed elements, each pre-programmed elementbeing independently executable relative each other pre-programmedelement such that an output of any of the pre-programmed elements is nota direct input to any other of the pre-programmed elements; receive viathe administrator facing UI a selection of two or more of thepre-programmed elements and a sequence for performing eachpre-programmed elements in the selection to form an exemplary routinethat includes the two or more of the pre-programmed elements; receivefrom the storefront server an indication of a first trigger eventcorresponding to an input at the customer facing UI, and in response toreceiving the indication of a trigger event, i) automatically creating afirst instance of the exemplary routine that includes an instance ofeach of the selected pre-programmed elements arranged for performance inaccordance with the sequence and being configured to perform tasksdefined by the pre-programmed elements and the sequence; and ii) settingto a pending execution status each instance of each of the selectedpre-programmed elements of the first instance of the exemplary routine;and a monitoring server coupled to the processing server and thedatabase, the monitoring server configured to: based on the executionstatus of each instance of the selected pre-programmed elements of thefirst instance of the exemplary routine, transmit a request to theprocessing server to initiate execution of the exemplary routineaccording to the sequence; and wherein the processing server is furtherconfigured to automatically execute the instances of the pre-programmedelements according to the sequence in response to the request from themonitoring server.
 107. The system of claim 106, wherein the processingserver is further configured to: detect an error that preventscompletion of at least one instance of the pre-programmed elements; andterminate the execution of the first instance of the exemplary routineupon detection of the error without user intervention.
 108. The systemof claim 107, wherein the processing server is further configured to:attempt to re-execute at least one instance of the pre-programmedelements associated with the detected error.
 109. The system of claim107, wherein the processing server is further configured to: detect atrigger event that triggers, without user intervention, a re-executionof the instance of at least one of the pre-programmed elements andwherein an error state that prevents the completion of the at least oneinstance arises after a subsequent trigger event is detected following apre-selected number of re-executions of the at least one instance of thepre-programmed element.
 110. The system of claim 107, wherein theprocessing server is further configured to: define a retry thresholdvalue for each of the pre-programmed elements; and attempt to re-executethe at least one instance of the pre-programmed elements associated withthe detected error in accordance with the retry threshold value. 111.The system of claim 107, wherein the processing server is furtherconfigured to: during execution of the instance of the exemplaryroutine, detect the absence of prescription authorization data needed tocomplete the execution of the instance of the exemplary routine; basedon the absence of the prescription authorization, automatically transmitan authorization form to an authorizing entity; receive an authorizationfacsimile of a completed form; automatically populate a prescriptionauthorization field based upon the received facsimile; and clear thedetected error to cause execution of the first instance of the exemplaryroutine to resume.
 112. The system of claim 106, wherein the processingserver is further configured to: simultaneously execute one or moreinstances of instances of pre-programmed elements in parallel.
 113. Thesystem of claim 106, wherein at least one pre-programmed element is along-running pre-programmed element that is programmed to cause otherpre-programmed elements within included in the first instance of theexemplary routine to at least one of: i) pause execution until thelong-running element reaches a completion state; ii) delay completionuntil the long-running element reaches the completion state.
 114. Thesystem of claim 106, wherein a failure to execute one instance of one ofthe pre-programmed elements does not prevent the execution andcompletion of another instance of the same pre-programmed element. 115.The system of claim 106, wherein the processing server is furtherconfigured to: receive from the storefront server, an indication of asecond trigger event corresponding to a second input at the customerfacing UI, and in response to receiving the indication of the secondtrigger event, i) automatically create a second instance of theexemplary routine that includes an instance of each of the selectedpre-programmed elements arranged for performance in accordance with thesequence and being configured to perform tasks defined by thepre-programmed elements and the sequence; and ii) set to a pendingexecution status each instance of each of the selected pre-programmedelements of the second instance of the exemplary routine, the monitoringserver further configured to, based on the execution status of eachinstance of the second exemplary routine, transmit a second request tothe processing server to initiate execution of the second exemplaryroutine according to the sequence, and the processing server furtherconfigured to, automatically execute the instances of the pre-programmedelements according to the sequence in response to the second requestfrom the monitoring server.
 116. The system of claim 115, wherein theexecution associated with the second request is independent of theexecution associated with the first request.
 117. The system of claim115, wherein the second instance of the exemplary routine differs fromthe first instance of the exemplary routine based on an aspect of apre-programmed element that was changed after the first instance ofexemplary routine was created.
 118. The system of claim 115, wherein theaspect of the pre-programmed element that changed includes at least oneof: substitution of pre-programmed elements, addition of apre-programmed element, alteration of a pre-programmed element,elimination of a preprogrammed element, a sequence change.